Skip to content

docs(installation): fix Zi installer raw URL#793

Merged
ss-o merged 14 commits into
nextfrom
bug-170
Jul 23, 2026
Merged

docs(installation): fix Zi installer raw URL#793
ss-o merged 14 commits into
nextfrom
bug-170

Conversation

@ss-o

@ss-o ss-o commented Jul 17, 2026

Copy link
Copy Markdown
Member

Summary

  • update the installer table's raw GitHub fallback from the removed lib/sh/install.sh path to the live public/sh/install.sh path
  • leave the loader URL and all installation commands unchanged

Verification

  • live HTTP check: new raw path serves content; old raw path returns 404
  • exact old URL absent; new URL appears once
  • one-line MDX diff and git diff --check: clean
  • local pnpm build unavailable because pnpm cannot initialize its database in the sandbox; CI is the build/lint gate

Related: z-shell/src#170

ss-o and others added 10 commits May 29, 2026 00:00
docs(zsh-lint): add generated-reference markers and seed content

Re-add the {/* zsh-lint:generated:start/end */} markers to the Zsh Lint
ecosystem page so the wiki-docs-sync pipeline from z-shell/zsh-lint has a
region to inject into. Seed the region with the current generated Go
reference so the first automated sync is a no-op rather than a failure.

The marked region is machine-managed — do not hand-edit; it is regenerated
from the repo's Go doc comments.

Co-authored-by: Salvydas Lukosius <ss-o@users.noreply.github.com>
docs(zsh-lint): sync generated reference from zsh-lint
ci(trunk): rename workflow/job to Trunk Code Quality to fix duplicate check context

The workflow and job were both named 'Trunk Check', colliding with the check
that trunk-io/trunk-action posts (also 'Trunk Check'). Two identically-named
check-runs confuse strict branch protection (required context 'Trunk Check'),
leaving PRs stuck in BLOCKED even when all checks pass. Renaming to the
org-conventional 'Trunk Code Quality' (matching other repos) leaves the
action's 'Trunk Check' as the sole required context. Fixes #757.

Co-authored-by: Salvydas Lukosius <ss-o@users.noreply.github.com>
The zsh package no longer ships 5.1.1 or 5.2.4 as selectable profiles
(z-shell/zsh#14). Remove the two stale 'zi pack' examples so the usage page
matches the available manifest profiles.
docs(zsh-lint): move tool documentation into community
Copilot AI review requested due to automatic review settings July 17, 2026 21:10
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 17, 2026

Copy link
Copy Markdown

Deploying zsh with  Cloudflare Pages  Cloudflare Pages

Latest commit: 898bd13
Status: ✅  Deploy successful!
Preview URL: https://a545e411.zsh.pages.dev
Branch Preview URL: https://bug-170.zsh.pages.dev

View logs

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Zi installation documentation to point the “GitHub RAW” installer fallback link to the current, live installer location in z-shell/src, keeping the short URL and installation commands unchanged.

Changes:

  • Replace the removed lib/sh/install.sh raw GitHub URL with public/sh/install.sh in the installer links table.

ss-o commented Jul 17, 2026

Copy link
Copy Markdown
Member Author

Agent handoff — merge is blocked on the failing Trunk check.

  • Cloudflare preview deploy: green
  • CodeQL: green
  • Trunk Code Quality run 29613790056: failed
  • No review threads

The local GitHub CLI token is invalid, so the required Actions log inspection cannot proceed. Next step: run gh auth refresh -h github.com (with repo/workflow access), then inspect PR #793/run 29613790056 and apply only the log-supported fix. Do not merge while Trunk is red.

@ss-o
ss-o merged commit 42004c1 into next Jul 23, 2026
4 of 6 checks passed
@ss-o
ss-o deleted the bug-170 branch July 23, 2026 11:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants